When should I create this type of policy?
Use the alert promotion policy when you want to create an incident based on alerts. This policy template helps you define how detailed, actionable incidents are created and managed.
What can I do with this policy?
You can route incidents to the right people, send notifications, create tickets when new incidents occur, and inform your colleagues when an incident is resolved.
Where can I find more information?
To learn more about policy templates and how to work with policies, see the product documentation.
View IBM docs
Policy details
Provide information to describe behavior for the policy.
Execution order
Use the slider or enter a value between 1-100 to set the execution order for the policy. Policies with a lower number are processed first. Values outside of 1-100 are reserved for suppression, some analytics, and preset policies that handle system needs. To see how your current policies are set, click on the number of policies listed below each range.
First (1-20)
21-40
41-60
61-80
Last (81-100)
Policy triggers
Define how the policy is triggered to create an incident. Once triggered, it will look for alerts that match the conditions you specify in order to take action.
When:
Policy is triggered
Condition sets
Add conditions that define which alerts the policy should look for and match. Important: In incident policies, only actions from the first matching condition set are executed. Learn more about condition sets and how they work.
- If all of these conditions are met:Alert propertiesIFValue of: alert.resource.applicationString: robot-shop
Then take the following actions:
Create an incidentIncident creationIBM Cloud Pak for AIOps will determine which of your alerts were caused by the same problem. If an active incident already exists for a given problem, a new incident will not be created.Specify hold off timeSet a priorityPriority
P1Priority 1Priority 1 is the highest.
Choose how to be notified (optional)Open a ticket (optional)Choose ticketing option(s).Focus sentinelFocus sentinelConnection unavailableThe previously selected ticket connection ServiceNow is no longer available. Please check the status of your connectors.Set incident assignee (optional)